Requirements Engineering - Getting Right from Wrong
نویسنده
چکیده
The neats: proponents of formal-based, knowledge-intensive smart systems to revolutionize the requirements process. The eventual success of the neat approach is less certain. There are several opinions of the answer to: ‘Can the neats ever playa significant role in requirements engineering?’: a. Never – the extra effort of doing things the neat way will always exceed the payoff. b. Hardly ever – only in very special circumstances, and/or for a minor portion of the overall development task. c. Eventually – sufficient advances in requirements work will result in neat tools that provide support for a revolutionized development process. d. Completely – AI systems will dominate the entire software process (and everything else).
منابع مشابه
Designing Software Services for Business Agility
One of the primary concerns when designing software services is identifying the right services to develop. A service at the right granularity with the right functionality can become a crucial asset in the enterprise software domain, while getting the granularity and functionality wrong may lead into a quagmire of interdependent services that are difficult to maintain and further develop wheneve...
متن کاملResearch Review: Globally Distributed Requirements Engineering and Agility
Getting requirements right is considered the most important and difficult part of the software development process. As organizations and stakeholders become more globally distributed, getting requirements right will pose a greater challenge. Today, organizations are offered a sophisticated array of multimedia meeting systems with video, audio and computer support for remotely specifying require...
متن کاملThe Top Risks of Requirements Engineering
0 7 4 0 7 4 5 9 / 0 1 / $ 1 0 . 0 0 © 2 0 0 1 I E E E T he worst thing that can happen in requirements engineering is that your set of requirements, however expressed, doesn’t accurately represent your users’ needs and consequently leads your team down the wrong development path. The whole point of requirements engineering is to steer your development toward producing the right software. If you...
متن کاملWhat's Wrong with Requirements Specification? An Analysis of the Fundamental Failings of Conventional Thinking about Software Requirements, and Some Suggestions for Getting it Right
We know many of our IT projects fail and disappoint. The poor state of requirements methods and practice is frequently stated as a factor for IT project failure. In this paper, I discuss what I believe is the fundamental cause: we think like programmers, not engineers and managers. We do not concentrate on value delivery, but instead on functions, on use-cases and on code delivery. Further, man...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
عنوان ژورنال:
دوره شماره
صفحات -
تاریخ انتشار 1991